- This allows to move all  all .java files from .groovy.
- Will prevent eclipse from tangling up in this setup
- make it possible to use Version from Java

…ormation-part1

```
> Task :plugins:ingest-user-agent:listElasticSearchClusters
Starting cluster: myTestCluster
   * myTestCluster: /home/alpar/work/elastic/elasticsearch/plugins/ingest-user-agent/foo
Asked to unClaimAndStop myTestCluster, since cluster still has 1 claim it will not be stopped

> Task :plugins:ingest-user-agent:testme UP-TO-DATE
Stopping myTestCluster, since no of claims is 0
```

- Meant to auto manage the clusters lifecycle
- Add integration test for cluster formation

…ormation-part2

…ormation-part2

```
> Task :plugins:ingest-user-agent:listElasticSearchClusters
Starting cluster: myTestCluster
   * myTestCluster: /home/alpar/work/elastic/elasticsearch/plugins/ingest-user-agent/foo
Asked to unClaimAndStop myTestCluster, since cluster still has 1 claim it will not be stopped

> Task :plugins:ingest-user-agent:testme UP-TO-DATE
Stopping myTestCluster, since no of claims is 0
```

- Meant to auto manage the clusters lifecycle
- Add integration test for cluster formation

Without this the tasks from different version can be ordered randomly
causing the snapshot test to fail ( i.e. creating snapshot for multiple
versions in the same location ).
Gradle happens to order them correctly when ran without "parallel" but
switches up the ordering when not.

Rather than fighting it, move to do it right before the runner

And check resulting artifact when starting up the cluster

Seems this hoggs some internal Gradle file locks, and messes with
Gradle's internals.

To be able to use process builder, the min java version for build was
bumped to 9.

This way building buildSrc will not be delayed for all invocations, and
will be less disruptive if integration tests fail

- support for multi project when not all projects apply the plugin.
    - add a test for it
- only register task liseners once per build ( not once per project )
- make the node name safe for paths and cluster name, even if it has `:` or `#` ( will be replaced by `-`)

Clean up the processes after even after `^C` is pressed.
The way Gradle does this is depending on the use of the Daemon,
but for us, even with the Daemon interupting it does not work as it
should and it eventually self terminates.

The downside is that the ES processes will be cleaned up with a delay
caused by  Gradle trying and failing to clean up the Daemon.

Allows to pass in closures that would evaluate at execution time.

…er-formation-part3

…ormation-part3

cmd.exe on windows does not close it's children, so we clean up
everything.

…ormation-part3

…ormation-part3